Dynamically modifying quality of service levels for resources in a networked computing environment

ABSTRACT

Embodiments of the present invention provide an approach for dynamically modifying Quality of Service (QoS) levels for resources (e.g., applications, processes, services, etc.) running in a networked computing environment. Specifically, embodiments of the present invention dynamically adjust transport level networking QoS parameters based on associated service level agreements (SLA) term. In a typical embodiment, a set of service level requirements associated with a resource running in the networked computing environment will first be identified (e.g., in a computer data structure). Then, the set of service level requirements will be mapped to a set of QoS parameters associated with a transport layer of the networked computing environment. A current performance of the resource within the transport layer will then be determined. Once the current performance has been determined, it will be further determined whether the current performance meets the set of service level requirements. Based on this determination/comparison, the set of QoS parameters can be adjusted accordingly.

TECHNICAL FIELD

Embodiments of the present invention generally relate to Quality ofService (QoS) levels. Specifically, embodiments of the present inventionrelate to dynamically modified QoS levels for resources running in anetworked computing environment (e.g., a cloud computing environment).

BACKGROUND

The networked computing environment (e.g., cloud computing environment)is an enhancement to the predecessor grid environment, whereby multiplegrids and other computation resources may be further enhanced by one ormore additional abstraction layers (e.g., a cloud layer), thus makingdisparate devices appear to an end-consumer as a single pool of seamlessresources. These resources may include such things as physical orlogical computing engines, servers and devices, device memory, andstorage devices, among others.

Challenges can exist in maintaining agreed upon Quality of Service (QoS)levels, especially in the transport layer of networked computingenvironments. For example, QoS priorities are typically established inadvance based upon the type of data packet being sent (e.g.,Transmission Control Protocol (TCP) versus User Datagram Protocol(UDP)), the source and/or destination of the network transmission, etc.Such approaches may not adequately compensate for shifting priorities orchanges in agreement-based QoS requirements.

SUMMARY

In general, embodiments of the present invention provide an approach fordynamically modifying Quality of Service (QoS) levels for resources(e.g., applications, processes, services, etc.) running in a networkedcomputing environment. Specifically, embodiments of the presentinvention dynamically adjust transport level networking QoS parametersbased on associated service level agreement (SLA) terms. In a typicalembodiment, a set of service level requirements associated with aresource running in the networked computing environment will first beidentified (e.g., in a computer data structure). Then, the set ofservice level requirements will be mapped to a set of QoS parametersassociated with a transport layer of the networked computingenvironment. A current performance of the resource within the transportlayer will then be determined. Once the current performance has beendetermined, it will be further determined whether the currentperformance meets the set of service level requirements. Based on thisdetermination/comparison, the set of QoS parameters can be adjustedaccordingly.

A first aspect of the present invention provides a computer-implementedmethod for dynamically modifying quality of service levels for aresource running in a networked computing environment, comprising:identifying, in a computer data structure, a set of service levelrequirements associated with the resource; mapping the set of servicelevel requirements to a set of quality of service parameters associatedwith a transport layer of the networked computing environment;determining a current performance of the resource within the transportlayer; determining whether the current performance meets the set ofservice level requirements; and adjusting, responsive to the set ofservice level requirements not being met, the set of quality of serviceparameters.

A second aspect of the present invention provides a system fordynamically modifying quality of service levels for a resource runningin a networked computing environment, comprising: a bus; a processorcoupled to the bus; and a memory medium coupled to the bus, the memorymedium comprising instructions to: identify, in a computer datastructure, a set of service level requirements associated with theresource; map the set of service level requirements to a set of qualityof service parameters associated with a transport layer of the networkedcomputing environment; determine a current performance of the resourcewithin the transport layer; determine whether the current performancemeets the set of service level requirements; and adjust, responsive tothe set of service level requirements not being met, the set of qualityof service parameters.

A third aspect of the present invention provides a computer programproduct for dynamically modifying quality of service levels for aresource running in a networked computing environment, the computerprogram product comprising a computer readable storage media, andprogram instructions stored on the computer readable storage media, to:identify, in a computer data structure, a set of service levelrequirements associated with the resource; map the set of service levelrequirements to a set of quality of service parameters associated with atransport layer of the networked computing environment; determine acurrent performance of the resource within the transport layer;determine whether the current performance meets the set of service levelrequirements; and adjust, responsive to the set of service levelrequirements not being met, the set of quality of service parameters.

A fourth aspect of the present invention provides a method for deployinga computer infrastructure for dynamically modifying quality of servicelevels for a resource running in a networked computing environment,comprising: providing a computer infrastructure being operable to:identify, in a computer data structure, a set of service levelrequirements associated with the resource; map the set of service levelrequirements to a set of quality of service parameters associated with atransport layer of the networked computing environment; determine acurrent performance of the resource within the transport layer;determine whether the current performance meets the set of service levelrequirements; and adjust, responsive to the set of service levelrequirements not being met, the set of quality of service parameters.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of this invention will be more readilyunderstood from the following detailed description of the variousaspects of the invention taken in conjunction with the accompanyingdrawings in which:

FIG. 1 depicts a cloud computing node according to an embodiment of thepresent invention.

FIG. 2 depicts a cloud computing environment according to an embodimentof the present invention.

FIG. 3 depicts abstraction model layers according to an embodiment ofthe present invention.

FIG. 4 depicts an Open Systems Interconnect (OSI) stack according to anembodiment of the present invention.

FIG. 5 depicts a system diagram according to an embodiment of thepresent invention.

FIG. 6 depicts a service decomposition process flow diagram according toan embodiment of the present invention.

FIG. 7 depicts a method flow diagram according to an embodiment of thepresent invention.

FIG. 8 depicts another method flow diagram according to an embodiment ofthe present invention.

The drawings are not necessarily to scale. The drawings are merelyschematic representations, not intended to portray specific parametersof the invention. The drawings are intended to depict only typicalembodiments of the invention, and therefore should not be considered aslimiting the scope of the invention. In the drawings, like numberingrepresents like elements.

DETAILED DESCRIPTION

Illustrative embodiments will now be described more fully herein withreference to the accompanying drawings, in which exemplary embodimentsare shown. This disclosure may, however, be embodied in many differentforms and should not be construed as limited to the exemplaryembodiments set forth herein. Rather, these exemplary embodiments areprovided so that this disclosure will be thorough and complete and willfully convey the scope of this disclosure to those skilled in the art.In the description, details of well-known features and techniques may beomitted to avoid unnecessarily obscuring the presented embodiments.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of this disclosure.As used herein, the singular forms “a”, “an”, and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. Furthermore, the use of the terms “a”, “an”, etc., do notdenote a limitation of quantity, but rather denote the presence of atleast one of the referenced items. It will be further understood thatthe terms “comprises” and/or “comprising”, or “includes” and/or“including”, when used in this specification, specify the presence ofstated features, regions, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, regions, integers, steps, operations, elements,components, and/or groups thereof.

As indicated above, embodiments of the present invention provide anapproach for dynamically modifying Quality of Service (QoS) levels forresources (e.g., applications, processes, services, etc.) running in anetworked computing environment. Specifically, embodiments of thepresent invention dynamically adjust transport level networking QoSparameters based on associated service level agreement (SLA) terms. In atypical embodiment, a set of service level requirements associated witha resource running in the networked computing environment will first beidentified (e.g., in a computer data structure). Then, the set ofservice level requirements will be mapped to a set of QoS parametersassociated with a transport layer of the networked computingenvironment. A current performance of the resource within the transportlayer will then be determined. Once the current performance has beendetermined, it will be further determined whether the currentperformance meets the set of service level requirements. Based on thisdetermination/comparison, the set of QoS parameters can be adjustedaccordingly.

It is understood in advance that although this disclosure includes adetailed description of cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded, automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active consumer accounts). Resource usage canbe monitored, controlled, and reported providing transparency for boththe provider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited consumer-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication-hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10, there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM, or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

The embodiments of the invention may be implemented as a computerreadable signal medium, which may include a propagated data signal withcomputer readable program code embodied therein (e.g., in baseband or aspart of a carrier wave). Such a propagated signal may take any of avariety of forms including, but not limited to, electro-magnetic,optical, or any suitable combination thereof. A computer readable signalmedium may be any computer readable medium that is not a computerreadable storage medium and that can communicate, propagate, ortransport a program for use by or in connection with an instructionexecution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium including, but not limited to, wireless,wireline, optical fiber cable, radio-frequency (RF), etc., or anysuitable combination of the foregoing.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a consumer to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via I/O interfaces22. Still yet, computer system/server 12 can communicate with one ormore networks such as a local area network (LAN), a general wide areanetwork (WAN), and/or a public network (e.g., the Internet) via networkadapter 20. As depicted, network adapter 20 communicates with the othercomponents of computer system/server 12 via bus 18. It should beunderstood that although not shown, other hardware and/or softwarecomponents could be used in conjunction with computer system/server 12.Examples include, but are not limited to: microcode, device drivers,redundant processing units, external disk drive arrays, RAID systems,tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as private, community,public, or hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms, and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes. In oneexample, IBM® zSeries® systems and RISC (Reduced Instruction SetComputer) architecture based servers. In one example, IBM pSeries®systems, IBM xSeries® systems, IBM BladeCenter® systems, storagedevices, networks, and networking components. Examples of softwarecomponents include network application server software. In one example,IBM WebSphere® application server software and database software. In oneexample, IBM DB2® database software. (IBM, zSeries, pSeries, xSeries,BladeCenter, WebSphere, and DB2 are trademarks of International BusinessMachines Corporation registered in many jurisdictions worldwide.)

Virtualization layer 62 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers;virtual storage; virtual networks, including virtual private networks;virtual applications and operating systems; and virtual clients.

In one example, management layer 64 may provide the functions describedbelow. Resource provisioning provides dynamic procurement of computingresources and other resources that are utilized to perform tasks withinthe cloud computing environment. Metering and pricing provide costtracking as resources are utilized within the cloud computingenvironment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.Consumer portal provides access to the cloud computing environment forconsumers and system administrators. Service level management providescloud computing resource allocation and management such that requiredservice levels are met. Service Level Agreement (SLA) planning andfulfillment provides pre-arrangement for, and procurement of, cloudcomputing resources for which a future requirement is anticipated inaccordance with an SLA. Further shown in management layer is Quality ofService (QoS) modification, which represents the functionality that isprovided under the embodiments of the present invention.

Workloads layer 66 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation; software development and lifecycle management; virtualclassroom education delivery; data analytics processing; transactionprocessing; and consumer data storage and backup. As mentioned above,all of the foregoing examples described with respect to FIG. 3 areillustrative only, and the invention is not limited to these examples.

It is understood that all functions of the present invention asdescribed herein typically may be performed by the QoS modificationfunctionality of management layer 64, which can be tangibly embodied asmodules of program code 42 of program/utility 40 (FIG. 1). However, thisneed not be the case. Rather, the functionality recited herein could becarried out/implemented and/or enabled by any of the layers 60-66 shownin FIG. 3.

It is reiterated that although this disclosure includes a detaileddescription on cloud computing, implementation of the teachings recitedherein are not limited to a cloud computing environment. Rather, theembodiments of the present invention are intended to be implemented withany type of networked computing environment now known or laterdeveloped.

As indicated above, embodiments of the present invention provide anapproach to dynamically adjust transport level networking based on theservice level agreements (SLAs) defined for associated resources such asapplications, processes, services, etc. This approach helps to ensurethat SLAs can be met, particularly for large heterogeneous environmentsas may be found in cloud computing environment installations.

One aspect of the embodiments of the present invention is that priorityand Quality of Service (QoS) delivered at the transport level (e.g.,Transmission Control Protocol/Internet Protocol (TCP/IP)) may bedynamically calculated and modified/updated based on service levelsassociated with resources. For example, a mission-critical applicationthat is being backed up may automatically change the QoS of the TCP/IPpackets to ensure that the backups complete on time, or an importantbusiness process may be in jeopardy of failing if priority is not givento a network transmission on a highly utilized switch. An aspect of thepresent invention is that such overriding concerns are given appropriateattention.

Referring now to FIG. 4, an illustrative Open Systems Interconnect (OSI)stack 70 according to an embodiment of the present invention is shown.As depicted, OSI stack 70 comprises the following layers:

Application layer 72: This is the layer at which communication partnersare identified, QoS is identified, user authentication and privacy areconsidered, and any constraints on data syntax are identified. Thislayer is typically not the application itself, although someapplications may perform application layer functions.

Presentation layer 74: This is a layer (sometimes called the syntaxlayer), usually part of an operating system, that converts incoming andoutgoing data from one presentation format to another (e.g., from a textstream into a popup window with the newly arrived text).

Session layer 76: This layer sets up, coordinates, and terminatesconversations, exchanges, and dialogs between the applications at eachend. Session layer 76 is associated with session and connectioncoordination.

Transport layer 78: This layer manages the end-to-end control (e.g.,determining whether all packets have arrived) and error-checking.Transport layer 78 works to ensure complete data transfer.

Network layer 80: This layer handles the routing of the data (e.g.,sending data in the right direction to the right destination on outgoingtransmissions and receiving incoming transmissions at the packet level).Network layer 80 performs routing and forwarding.

Data link layer 82: This layer provides synchronization for the physicallevel and does bit-stuffing for strings of 1's in excess of 5. Data linklayer 82 furnishes transmission protocol knowledge and management.

Physical layer 84: This layer conveys the bit stream through the networkat the electrical and mechanical level. Physical layer 84 provides thehardware means of sending and receiving data on a carrier.

In general, embodiments of the invention dynamically modify QoSparameters for running resources at transport layer 78 based onassociated service level requirements (e.g., as set forth in associatedSLAs).

Referring now to FIG. 5, a system diagram according to an embodiment ofthe present invention is shown. As depicted in FIG. 5, a QoSmodification engine (engine 90) is provided. In general, engine 90 canbe implemented as one or more programs such as program 40 of FIG. 1 andis capable of implementing the functionality discussed herein such asthat depicted by QoS modification function of management layer 64 ofFIG. 3. Moreover, engine 90 generally comprises SLA QoS system 92, SLAinsertion system 94, and network packet inspection system 96. Thesesystems generally have the following functions:

SLA QoS system 92 accesses a database 98 that stores SLA relatedinformation for the services, applications and business processescurrently being executed in the networked computing environment. Forexample, a credit card processing service may have an SLA that statesthat the process should take no more than ten seconds. A batch job mayhave an SLA which states that the process should take no more than 4hours. SLA QoS system 92 takes such SLAs and writes the SLAs to adatabase that is accessible by network package inspection system 96.Once stored, the SLA QoS system 92 continues to monitor the services andbusiness processes, and updates the database with priorities of eachbased on current SLA attainment. For example, the credit card processingand batch job services may have an entry in the database similar to thefollowing:

Unique Transaction SLA Current Service Identifier Identification MetricStatus Flag Credit 1234 1 10 seconds 5 seconds Medium Card remainingBatch 4321 2  4 hours 3 hours Low Job remaining

SLA QoS system 92 continually checks processing of the service andupdates the database. For example, after a period of time, the table maychange to:

Transaction Unique Identification SLA Current Service Identifier SLAMetric Status Flag Credit 1234 1 10 seconds 1 second High Card remainingBatch 4321 2  4 hours 3 hours Low Job remainingEach column of these tables is described below:

Service: The name of the service that has SLAs associated therewith.

Unique Identifier (UID): A unique identifier used to identify theservice. In this example, ‘1234’ means the credit card service.

Transaction ID: The specific transaction being processed, because theservice may be instantiated more than once.

SLA: The SLA metric associated with the transaction.

Current Status How much time is left before the SLA will fail.

Flag: Failed, Critical, High, Medium, Low. Based on the current status,this indicates the priority that should be given to the network trafficQoS at this point in time. It is noted that other embodiments could usesimilar grading factors, and that an implementation of this inventionneed not use exactly these terms.

Regardless, SLA QoS system 92 continually updates the table(s) andupdates the priority flag based on current processing. In this example,the credit card service, transaction 1, will fail the service level inone second, so the flag is changed to ‘high’-showing that there is aneed to push the QoS of the network traffic associated with the serviceto be a high priority. The batch job service flag remains low due to theremaining time before SLA failure. It is further noted that, in anotherembodiment, the timing between polls can be modified based on the SLA.For example, the batch job may only need to be polled every 30 minutes,whereas the credit card service may need to be polled every second. Suchpolling frequency modification can be executed simply, using a varietyof well-known methods.

SLA insertion system 94 can be implemented via software in theapplication which initiates network data transfers. In this invention,the system will insert a unique identifier into the transport layer 100(also shown as transport layer 78 of FIG. 4) of each data packet beingsent, so as to associate it with the service for which the networkconnection is being used. SLA insertion system 94 may read database 98from the SLA QoS system 92 to find the UID of the service to embed intothe packets being sent. For example, all network packets associated withthe credit card service are given the UID of ‘1234’. It can berecognized that SLA insertion system 94 may be implemented in software,hardware (including firmware), or various combinations of associatedlogic.

Network packet inspection system 96 may be embedded into networkhardware 92 such as key routers and/or switches 102 within the ITenvironment. Much as a router looks at the network layer to determinerouting of TCP/IP packets, network packet inspection system 96 looks attransport layer 100 to determine whether the UID has been set. If a UIDis found, and optionally if not, network packet inspection system 96looks at the database 98 to determine whether there is a flag todetermine overall priority of the network packet. If a flag is found,network packet inspection system 96 uses the flag to change the QoS ofthe packet to improve bandwidth or throttle other (less important)network communications.

Illustrative Implementation

The invention is typically implemented through one or more of the threesystems identified above with an associated method. FIG. 6 shows anexample of two services 110A-B (also referred to herein as Service 1 andService 2) with a breakdown of the network communications upon whichboth services rely. In this example, Service 1 requires two networktransfers of data between Virtual Local Area Networks (VLANs) R1 and aseparate data transfer R2. Service 2 requires a data push to the portR2-R3.

Referring back to FIG. 5, when a new service is rolled out, theserelationships may be calculated, either manually by the software/ITdesigner, or by automatic means. A determination can then be made as towhich packets need to have the UID inserted. Networks that are notwithin the control of the enterprise, for example, do not need to beanalyzed by network packet inspection system 96. Once this determinationis completed, such information may be fed to the SLA QoS system 92 suchthat it knows which data transfers affect the service. SLA QoS system 92may optionally be updated (e.g., periodically, continuously, etc.) as tocurrent processing status of each business process or service. This canbe achieved by communication to a submission engine or job scheduler(e.g., a service request system. It may also communicate directly to thekey application server that is managing each service to determinecompletion state. In either case, database 98 may be updated. Next, SLAinsertion system 94 will be embedded into each computer that initiates adata connection (e.g., a credit card authorization system). Then, SLAinsertion system 94 adds the UID to each data packet beforetransmission.

In a typical embodiment, network packet inspection system 96functionality can be included in any key routers or switches along thepath of possible communications bottlenecks. Such network packetinspection system 96 functionality can be integrated as a hardwareappliance or included as part of the router or switch software. Networkpacket inspection system 96 uses database 98 to make decisions for QoSpriority. It is noted that “database” as used in this description couldtake on a variety of forms, including databases such as IBM® DB2® (IBM,DB2, and related terms are trademarks of IBM Corp. in the United Statesand/or other countries), or it could take on other forms such as purelymemory-resident data structures allowing for rapid recall andcorrelation of relevant information.

Regardless, FIG. 7 depicts an illustrative method flow diagram outliningthe process steps to be used in accordance with the embodiments of thepresent invention. It is noted that one or more of these steps could berearranged without loss of functionality.

Step S1: “Determine current SLAs” is generally (but not necessarily)performed only once. This could be entered manually by a systemadministrator, or it could be captured through automated means (e.g.extracted from a table of SLAs). Furthermore, since periodic SLA changesmay occur, updates can be captured through either push or pull of suchinformation. Regardless of form, this step captures the base SLAs foreach service.

Step S2: Determine current SLA attainments. The SLA QoS systemcommunicates with the job scheduler, portal, or application running theservice to determine whether the service is being executed. If theservice can be executed concurrently by more than one thread, the QoSsystem chooses a transaction identifier and also stores the identifierin the database.

Step S3: The SLA QoS system continually updates and stores the SLAcurrent attainment and flag information into the database.

Step S4: Assuming that all packets associated with services have the QoSfield in the transport field set (by the insertion system), the networkpacket inspection system running on the router scans each incomingpacket.

Step S5: For each packet found, the network packet inspection systemchecks the database to determine what the relative priority of the QoSshould be for that packet and modifies the QoS accordingly.

Step S6: The network packet inspection system may look at currentbandwidth utilization to determine whether throttling of non-servicealigned packets is required (e.g., personal web browsing, Domain NameSystem (DNS) requests, email, etc.).

Step S7: Network packet inspection system modifies the QoS flag of eachpacket as necessary to optimize throughput of networking packets.

Through use of the techniques outlined herein, service level achievementcan be strengthened and overall revenue/cost structures optimized forthe adopting organization. Furthermore, this approach can benefit (amongothers) organizations that have large heterogeneous traffic mixes, suchas are often found with providers who offer various cloud computingservices.

Referring now to FIG. 8, another method flow diagram according to anembodiment of the present invention is shown. In step T1 is a set ofservice level requirements (as identified from at least one SLA)associated with a resource (e.g., an application, a process, a service,etc.) running in a networked computing environment is identified in acomputer data structure. In step T2, the set of service levelrequirements are mapped to a set of QoS parameters associated with atransport layer of the networked computing environment. In step T3, acurrent performance of the resource within the transport layer isdetermined. In step T4, it is determined whether the current performancemeets the set of service level requirements. If so, the process can berepeated for other resources running in the networked computingenvironment. However, responsive to the set of service levelrequirements not being met, the set of QoS parameters is adjusted instep T5. In general, the adjusting of the QoS parameters can include oneor more of the following: assigning a higher priority level to a set ofdata packets being sent pursuant to the running of resource in thenetworked computing environment, allocating additional bandwidth to theset of data packets, and/or modifying a Quality of Service flagassociated with the set of data packets.

While shown and described herein as a dynamic QoS modification solution,it is understood that the invention further provides various alternativeembodiments. For example, in one embodiment, the invention provides acomputer-readable/useable medium that includes computer program code toenable a computer infrastructure to provide dynamic QoS modificationfunctionality as discussed herein. To this extent, thecomputer-readable/useable medium includes program code that implementseach of the various processes of the invention. It is understood thatthe terms computer-readable medium or computer-useable medium compriseone or more of any type of physical embodiment of the program code. Inparticular, the computer-readable/useable medium can comprise programcode embodied on one or more portable storage articles of manufacture(e.g., a compact disc, a magnetic disk, a tape, etc.), on one or moredata storage portions of a computing device, such as memory 28 (FIG. 1)and/or storage system 34 (FIG. 1) (e.g., a fixed disk, a read-onlymemory, a random access memory, a cache memory, etc.).

In another embodiment, the invention provides a method that performs theprocess of the invention on a subscription, advertising, and/or feebasis. That is, a service provider, such as a Solution Integrator, couldoffer to provide dynamic QoS modification functionality. In this case,the service provider can create, maintain, support, etc., a computerinfrastructure, such as computer system 12 (FIG. 1) that performs theprocesses of the invention for one or more consumers. In return, theservice provider can receive payment from the consumer(s) under asubscription and/or fee agreement and/or the service provider canreceive payment from the sale of advertising content to one or morethird parties.

In still another embodiment, the invention provides acomputer-implemented method for dynamic QoS modification. In this case,a computer infrastructure, such as computer system 12 (FIG. 1), can beprovided and one or more systems for performing the processes of theinvention can be obtained (e.g., created, purchased, used, modified,etc.) and deployed to the computer infrastructure. To this extent, thedeployment of a system can comprise one or more of: (1) installingprogram code on a computing device, such as computer system 12 (FIG. 1),from a computer-readable medium; (2) adding one or more computingdevices to the computer infrastructure; and (3) incorporating and/ormodifying one or more existing systems of the computer infrastructure toenable the computer infrastructure to perform the processes of theinvention.

As used herein, it is understood that the terms “program code” and“computer program code” are synonymous and mean any expression, in anylanguage, code, or notation, of a set of instructions intended to causea computing device having an information processing capability toperform a particular function either directly or after either or both ofthe following: (a) conversion to another language, code, or notation;and/or (b) reproduction in a different material form. To this extent,program code can be embodied as one or more of: an application/softwareprogram, component software/a library of functions, an operating system,a basic device system/driver for a particular computing device, and thelike.

A data processing system suitable for storing and/or executing programcode can be provided hereunder and can include at least one processorcommunicatively coupled, directly or indirectly, to memory elementsthrough a system bus. The memory elements can include, but are notlimited to, local memory employed during actual execution of the programcode, bulk storage, and cache memories that provide temporary storage ofat least some program code in order to reduce the number of times codemust be retrieved from bulk storage during execution. Input/outputand/or other external devices (including, but not limited to, keyboards,displays, pointing devices, etc.) can be coupled to the system eitherdirectly or through intervening device controllers.

Network adapters also may be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems,remote printers, storage devices, and/or the like, through anycombination of intervening private or public networks. Illustrativenetwork adapters include, but are not limited to, modems, cable modems,and Ethernet cards.

The foregoing description of various aspects of the invention has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formdisclosed and, obviously, many modifications and variations arepossible. Such modifications and variations that may be apparent to aperson skilled in the art are intended to be included within the scopeof the invention as defined by the accompanying claims.

What is claimed is:
 1. A computer-implemented method for dynamicallymodifying quality of service levels for a resource running in anetworked computing environment, comprising: identifying, in a computerdata structure, a set of service level requirements associated with theresource; mapping the set of service level requirements to a set ofquality of service parameters associated with a transport layer of thenetworked computing environment; determining whether a unique identifierhas been inserted into the transport layer for each of a set of datapackets to associate each of the set of data packets with a resource; ifthe unique identifier has not been inserted, checking a database todetermine whether a priority for the data packet has been set;determining a current performance of the resource within the transportlayer; determining whether the current performance meets the set ofservice level requirements; and adjusting, responsive to the set ofservice level requirements not being met, the set of quality of serviceparameters.
 2. The computer-implemented method of claim 1, the resourcecomprising at least one of the following: an application, a process, ora service.
 3. The computer-implemented method of claim 1, the set ofservice level requirements being identified from at least one servicelevel agreement associated with the resource.
 4. Thecomputer-implemented method of claim 1, further comprising inserting theunique identifier into the transport layer for the each of a set of datapackets, the unique identifier being sent pursuant to the running of theresource in the networked computing environment.
 5. Thecomputer-implemented method of claim 4, the adjusting comprisingassigning a higher priority level to the set of data packets.
 6. Thecomputer-implemented method of claim 4, the adjusting comprisingallocating of additional bandwidth to the set of data packets.
 7. Thecomputer-implemented method of claim 4, the adjusting comprisingmodifying a quality of service flag associated with the set of datapackets.
 8. A system for dynamically modifying quality of service levelsfor a resource running in a networked computing environment, comprising:a bus; a processor coupled to the bus; and a memory medium coupled tothe bus, the memory medium comprising instructions to: identify, in acomputer data structure, a set of service level requirements associatedwith the resource; map the set of service level requirements to a set ofquality of service parameters associated with a transport layer of thenetworked computing environment; determine whether a unique identifierhas been inserted into the transport layer for each of a set of datapackets to associate each of the set of data packets with a resource; ifthe unique identifier has not been inserted, check a database todetermine whether a priority for the data packet has been set; determinea current performance of the resource within the transport layer;determine whether the current performance meets the set of service levelrequirements; and adjust, responsive to the set of service levelrequirements not being met, the set of quality of service parameters. 9.The system of claim 8, the resource comprising at least one of thefollowing: an application, a process, or a service.
 10. The system ofclaim 8, the set of service level requirements being identified from atleast one service level agreement associated with the resource.
 11. Thesystem of claim 8, the memory medium further comprising instructions toinsert the unique identifier into the transport layer for the each of aset of data packets being sent pursuant to the running of the resourcein the networked computing environment.
 12. The system of claim 11, thememory medium further comprising instructions to assign a higherpriority level to the set of data packets.
 13. The system of claim 11,the memory medium further comprising instructions to allocate additionalbandwidth to the set of data packets.
 14. The system of claim 11, thememory medium further comprising instructions to modify a quality ofservice flag associated with the set of data packets.
 15. A computerprogram product for dynamically modifying quality of service levels fora resource running in a networked computing environment, the computerprogram product comprising a non-transitory computer readable storagemedium, and program instructions stored on the non-transitory computerreadable storage medium, to: identify, in a computer data structure, aset of service level requirements associated with the resource; map theset of service level requirements to a set of quality of serviceparameters associated with a transport layer of the networked computingenvironment; determine whether a unique identifier has been insertedinto the transport layer for each of a set of data packets to associateeach of the set of data packets with a resource; if the uniqueidentifier has not been inserted, check a database to determine whethera priority for the data packet has been set; determine a currentperformance of the resource within the transport layer; determinewhether the current performance meets the set of service levelrequirements; and adjust, responsive to the set of service levelrequirements not being met, the set of quality of service parameters.16. The computer program product of claim 15, the resource comprising atleast one of the following: an application, a process, or a service. 17.The computer program product of claim 15, the set of service levelrequirements being identified from at least one service level agreementassociated with the resource.
 18. The computer program product of claim15, the non-transitory computer readable storage medium furthercomprising instructions to insert the unique identifier into thetransport layer for the each of a set of data packets being sentpursuant to the running of the resource in the networked computingenvironment.
 19. The computer program product of claim 18, thenon-transitory computer readable storage medium further comprisinginstructions to assign a higher priority level to the set of datapackets.
 20. The computer program product of claim 18, thenon-transitory computer readable storage medium further comprisinginstructions to allocate additional bandwidth to the set of datapackets.
 21. The computer program product of claim 18, thenon-transitory computer readable storage medium further comprisinginstructions to modify a quality of service flag associated with the setof data packets.
 22. A method for deploying a computer infrastructurefor dynamically modifying quality of service levels for a resourcerunning in a networked computing environment, comprising: providing acomputer infrastructure being operable to: identify, in a computer datastructure, a set of service level requirements associated with theresource; map the set of service level requirements to a set of qualityof service parameters associated with a transport layer of the networkedcomputing environment; determine whether a unique identifier has beeninserted into the transport layer for each of a set of data packets toassociate each of the set of data packets with a resource; if the uniqueidentifier has not been inserted, check a database to determine whethera priority for the data packet has been set; determine a currentperformance of the resource within the transport layer; determinewhether the current performance meets the set of service levelrequirements; and adjust, responsive to the set of service levelrequirements not being met, the set of quality of service parameters.